fix: bump moby/spdystream to v0.5.1 (CVE-2026-35469)#19
Merged
Conversation
Resolves CVE-2026-35469 reported via Docker Scout in the spdystream indirect dependency (pulled in via k8s.io/client-go). Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Docker Scout reports CVE-2026-35469 in the
github.com/moby/spdystreamindirect dependency (pulled in viak8s.io/client-go). The vulnerability is fixed inv0.5.1.Change
Bumped
github.com/moby/spdystreamfromv0.5.0→v0.5.1ingo.mod/go.sum. No other dependencies were changed.Verification
go build ./...govulncheck ./...confirms CVE-2026-35469 is no longer present and no new vulnerabilities were introduced